* Adjusted the version of `PowerShellBuild` from '0.7.2' to '0.6.1' to maintain compatibility with the current setup.

* Reformatted YAML for consistency in spacing.
* Separated Bootstrap and Test steps for clarity in the CI process.

* Changed `properties` to `Properties` for consistency.
* Removed unnecessary task definitions and streamlined the `Test` task.
* Adjusted comments for clarity regarding CI behavior.

PowerShellBuild 0.6.1 has no mechanism to override the Build task's
dependency chain from outside its psake file. 0.7.x introduced
$PSBBuildDependency which can be pre-set before -FromModule loads
the module, preventing BuildHelp (and GenerateMarkdown) from running.

GenerateMarkdown is not needed in the test pipeline and
Build-PSBuildMarkdown has a Remove-Module scope issue specific to
PSDepend that causes it to attempt removing 'platyPS' instead of
'PSDepend', failing because platyPS is required by PowerShellBuild.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…exts

Bare Set-StrictMode calls in Context block bodies run during Pester 5's
discovery phase, not test execution — the It blocks never actually ran
under strict mode. Wrapping in BeforeAll/AfterAll ensures strict mode
applies during execution and is cleaned up after each context.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Four related fixes in one pass:

1. Prefix all outer Describe BeforeAll variables with $script: so they
   are visible in It blocks during test execution.
2. Prefix all inner Context BeforeAll variables with $script: and update
   the three parameter-validation It assertions to use $script: reads.
3. Add $helpParameters/$helpParameterNames to BeforeDiscovery so that
   -ForEach $helpParameterNames on the inner Context is non-empty at
   discovery time (BeforeAll runs too late for ForEach evaluation).
4. Replace undefined $parameterNames with $script:commandParameterNames.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Mocks defined inside It blocks are scoped to that It and collapse when
it exits, making Should -Invoke assertions fragile and mixing arrangement
with assertion. Moved mocks to BeforeAll for the five affected contexts
(PSGalleryModule Imports, AddToPath-install, SkipPublisherCheck,
AllowPrerelease; PSGalleryNuget Imports, AddToPath-install) and added
-Scope Context to all Should -Invoke calls in those contexts.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

The two AddToPath-install contexts (PSGalleryModule and PSGalleryNuget)
restored $ENV:PSModulePath inside the It body. If the assertion before
that line failed, the env var would remain modified for the rest of the
run. Moved cleanup to AfterEach so it runs unconditionally. Also
switched to explicit $script:ExistingPSModulePath to match how the
variable is set in the outer BeforeAll.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Invoke-WebRequest had no timeout, causing the suite to hang on slow or
unreachable URLs. Added -TimeoutSec 10. Tagged the It blocks -Tag
'Acceptance' so offline CI runs can exclude them with -ExcludeTag
Acceptance.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Git, FileDownload, and FileSystem Describe blocks all skip on non-Windows
via -Skip:\$nonWindows. The Chocolatey block only had -Tag 'WindowsOnly',
meaning it would still execute on Linux/macOS runners unless callers
explicitly excluded the tag. Aligned it with the other Windows-only blocks.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

The 'Installs Packages' Context was commented out pending Pester issue
#604 (mock parameter binding), which is resolved in Pester 5. Rewrote
it with BeforeAll, $script: variables, and -Scope Context.

Removed -Skip and the stale AppVeyor comment from 'Latest package
required' — the flakiness was caused by mock bleeding across contexts,
which Pester 5 scope isolation eliminates. Also moved all inline Mock
calls from It bodies in 'Same package version exists' and the latest
context into BeforeAll blocks.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Cover three scenarios missing from the existing success-path suite:
- -Tags filter returns only dependencies with matching tags
- -Tags with no match returns nothing
- -InputObject hashtable is parsed as PSGalleryModule by default

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…l-Dependency, Invoke-DependencyScript

Four previously untested public functions now have dedicated Describe
blocks:

- Get-PSDependType: returns typed objects, filters by wildcard, Supported
  is bool, throws on invalid path
- Get-PSDependScript: returns hashtable, all values are real paths, throws
  on invalid path
- Install-Dependency: pipeline from Get-Dependency calls Install-Module
- Invoke-DependencyScript: Command type returns output, non-existent action
  warns rather than throws, Test action with -Quiet returns bool

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

- Add .EXAMPLE to Get-Dependency help (fixes help test failures)
- Fix .LINK URL typo PowerShellOr -> PowerShellOrg across all public functions
- Filter null URIs in Help.tests.ps1 to prevent FunctionInfo-as-Uri errors
  when .LINK entries are non-URL (function names, about pages)
- Strip -Force from PSBoundParameters before splatting to Invoke-DependencyScript,
  which has no -Force parameter
- Add -ModuleName PSDepend to all Mock/-Invoke assertions for commands called
  from within PSDepend dependency scripts (Install-Module, Save-Module, Get-Module,
  Find-Module, Import-Module, Get-PSRepository, Install-Package, Get-Package,
  Find-Package, Get-PackageSource, Get-NodeModule, Install-NodeModule, Test-Dotnet,
  Install-Dotnet, Get-DotnetVersion, Get-Command, Test-Path) so Pester v5 intercepts
  them at the correct module scope

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

- Use @{} + $PSBoundParameters instead of .Clone() to copy PSBoundParameters
  into a mutable hashtable (PSBoundParametersDictionary has no Clone method)
- Inject stub functions for PackageManagement commands into PSDepend's module
  scope via & (Get-Module PSDepend) { ... } so -ModuleName PSDepend mocks
  can resolve them; remove now-redundant inline function redefinitions in
  individual Package contexts; add AfterAll cleanup
- Add -ModuleName PSDepend to all mocks in Git, FileDownload, PSGalleryNuget,
  and FileSystem Describe blocks — these are Windows-only sections where
  Invoke-ExternalCommand, Get-WebFile, Find-NugetPackage, Copy-Item,
  Import-LocalizedData, Import-Module, Test-Path, New-Item, Push-Location,
  Pop-Location, and Set-Location all resolve inside PSDepend's module scope
- Fix Npm: add -ModuleName PSDepend to Push-Location and Pop-Location in
  both Npm contexts; fix `return true` string bug to `return $true`

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

- Package: add [cmdletbinding()]param() to Get-PackageSource stub so Pester
  can generate a valid v5 mock proxy without ParameterBindingException
- Package: add Mock Get-PackageSource -ModuleName PSDepend to the three
  contexts that were hitting the real cmdlet (Same version, Latest, Test-Dependency)
- Npm: fix ParameterFilter from { $Target -eq 'Global' } to { $Global -eq $true };
  Npm.ps1 calls Get-NodeModule -Global (switch), not -Target 'Global'
- Chocolatey 'installs Chocolatey': add -ModuleName PSDepend to Get-Command
  and Invoke-WebRequest mocks and Should -Invoke assertions
- Chocolatey skip/install contexts: replace unmockable inline helpers
  (Get-ChocoInstalledPackage, Get-ChocoLatestPackage, Invoke-ChocoInstallPackage)
  with Invoke-ExternalCommand mocks; the inline functions are dot-sourced into
  local scope and shadow module-scope mocks, but Invoke-ExternalCommand is a
  PSDepend private module function that Pester can intercept; use ParameterFilter
  on --local-only (installed), list-no-local-only (latest), and upgrade (install)
  to distinguish the three call types and return appropriate CSV-formatted data

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Without the script: scope qualifier, function definitions inside
& (Get-Module PSDepend) { function Foo { } } are created in a temporary
scope that vanishes when the scriptblock returns. The stubs were never
actually shadowing the real cmdlets.

Pester's mock proxy was being generated from the real Get-Package /
Install-Package / Find-Package / Get-PackageSource cmdlets (from
AnyPackage on Linux, PackageManagement elsewhere) — whose multi-parameter
-set definitions failed to bind our test splats with
ParameterBindingException: Parameter set cannot be resolved.

Using function script:Foo persists the stub in the module's script scope
so Get-Command -Module PSDepend resolves to the stub, and Pester generates
the proxy from the stub's simple param signature.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Updated the path for uploading test results from `./Output/testResults.xml` to `./Tests/out/testResults.xml` to ensure proper artifact handling.